-
Notifications
You must be signed in to change notification settings - Fork 2
feat(dom): Add toHaveClass , toHaveAllClasses, and toHaveAnyClass assertions #134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
6827334
to
18f9d98
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great @fonsiher. Thank you!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good so far, but I think we can improve things if we create 3 assertions instead of one 🙂
6e6062d
to
a831c90
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we rename the PR to contain all the toHaveClass , toHaveAllClasses, toHaveAnyClass 👀 please?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good! I left some comments and suggestions. Let me know if you have any questions 🙂
a831c90
to
8805f6f
Compare
0d3c0c6
to
e512c76
Compare
Thanks for your review @JoseLion , you're right, I've added the prop to the testing function and now are using getByText for render the element for Testing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! Nice work @fonsiher 🎉
Added the toHaveClass matcher.